Establishing machine type communications

ABSTRACT

A method for establishing a machine type communication includes receiving a connection request for a machine type communication from a device. The connection request includes an authentication credential for the device. A shared subscriber identity module (SIM) parameter for the machine type communication is obtained based on the authentication credential.

TECHNICAL FIELD

This disclosure relates to data transmission in communication systemsand, more specifically, to establishing machine type communications.

BACKGROUND

In an Internet of Things (IoT) environment, machines can be connectedwith other machines or data collection points. In some cases, thesemachines can be monitored and the operation data of these machines canbe collected and analyzed. This data can be transmitted in a machinetype communication. As more and more devices are connected, machine typecommunication has expanded rapidly and may have a significant impact onthe operation of communication networks.

DESCRIPTION OF DRAWINGS

FIG. 1 is an example communication system that establishes a machinetype communication.

FIG. 2 is a message flow diagram illustrating an example process forestablishing a machine type communication.

FIG. 3 is a message flow diagram illustrating another example processfor establishing a machine type communication.

FIG. 4 is a diagram illustrating an example layered protocol structurefor establishing a machine type communication.

FIG. 5 is a flowchart illustrating an example method for establishing amachine type communication.

FIG. 6 is a flowchart illustrating another example method forestablishing a machine type communication.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

The present disclosure is directed to establishing a machine typecommunication. In a machine type communication, equipment and devicesmay generate data based on one or more attributes that need to bemonitored. This data may be sensed, collected, and transmitted to acollection point, where the data may be further analyzed. For example, asmart meter may sense the energy usage of a residence and provide thedata to a utility company. The utility company may analyze the data inmanaging power, dimensioning the power, and delivering the power tohomes in different neighborhoods of the city.

In some cases, the machine type communication data can be transmittedusing one of several local area network or wide area networktechnologies. However, these technologies may not provide a low cost andefficient access solution for wide area coverage. For example, Zigbee,WiFi, and Bluetooth are local area networks that may transmit over ashort distance. Cable or Internet modems are available indoors inbuildings, but may not be able to provide a ubiquitous coverage over awide area, such as outdoors. Cellular technology provides wide-areacoverage, but may be expensive, particularly when factoring in the costof a cellular modem, which may include a communication module withsecond generation (2G), third generation (3G), and fourth generation(4G) capabilities, in addition to the cost of a subscription for aregular data channel data over a cellular network. Even a low datamonitoring system, such as an alarm monitoring system, may have a retailprice of $5/month. Therefore, using current cellular technology toprovide machine type communication (MTC) may be costly for severalapplications.

In some implementations, a low-cost machine type communication may beestablished. A MTC device may obtain a shared access manifest parameter.The MTC device may establish a communication channel using the sharedaccess manifest parameter. The MTC device may transmit a MTC data packetusing the communication channel. After the transmission, the sharedaccess manifest parameter may be reused by a different MTC device for adifferent machine type communication.

FIG. 1 is an example communication system 100 that establishes a machinetype communication. For example, a connection request for a machine typecommunication may be received from a MTC device. The connection requestmay include an authentication credential for the MTC device. In someimplementations, the MTC device may be enabled with Long Term Evolution(LTE) communication capability that is configured for the machine typecommunication. A shared subscriber identity module (SIM) parameter forthe machine type communication may be obtained based on theauthentication credential. In some implementations, obtaining the SIMparameter may include sending the authentication credential to a devicemanagement server and receiving the shared SIM parameter in response tothe authentication credential.

In some implementations, the shared SIM parameter may be transmitted tothe MTC device. In some implementations, the shared SIM parameter may beencrypted by a public key of the MTC device. In some implementations, aregistration request may be received from the MTC device. Theregistration request may include the shared SIM parameter. The MTCdevice may be registered with a cellular network using the shared SIMparameter. A data packet may be received from the MTC device for themachine type communication. In some implementations, a deregistrationindication may be received from the MTC device. In response to thederegistration indication, a release message may be sent. The releasemessage may release the shared SIM parameter. In some implementations, amachine type communication channel for the MTC device may be establishedusing the shared SIM parameter independent of sending the shared SIMparameter to the MTC device.

Establishing a machine type communication according to methods andsystems described herein may provide one or more advantages. Forexample, by using a shared SIM parameter among multiple devices, thecost of providing access for the machine type communication can besignificantly reduced. Furthermore, a MTC device that is configured fora machine type communication may include a reduced set of circuitcomponents and support a simplified communication protocol. Therefore,the cost of making such MTC device can also be reduced. Furthermore,using an authentication and Access server (AAS) to authenticate a MTCdevice and encrypt a shared SIM parameter may increase the security ofmachine type communication. Other advantages will be apparent to thoseof ordinary skill in the art.

At a high level, the example communication system 100 includes a device106 that is coupled to a sensor 104. The sensor 104 is communicativelycoupled to a communication module (CM) 102. The example communicationsystem 100 also includes a device management server (DMS) 120 that isconfigured to communicate with an access network (AN) 110, anAuthentication and Access Sever (AAS) 122, and an application platform140. The communication may occur in any appropriate manner, such as overan Internet cloud 130. The AN 110 is also configured to communicate withthe CM 102.

As illustrated, the example communication system 100 includes the device106 that is coupled to the sensor 104. The device 106 represents adevice that is configured to generate data for monitoring. Examples ofthe device 106 includes white goods, consumer electronics, factoryautomation, transport vehicles, assets such as containers and fleetvans, retail goods, etc. The sensor 104 represents hardware, software,applications or a combination thereof that can be used to sense dataassociated with the device 106, or the environment in which the device106 is located.

In one example, the device 106 represents an electricity meter thatrecords energy usage. In some cases, the sensor 104 can include a dataconverter and a microprocessor. The microprocessor can be configured tocontinuously monitor the device 106 and receive recorded energy usage.The data converter can convert analog information from the device 106 todigital data that the microprocessor can process. The sensor 104 cansend data sensed to the CM 102 for transmission. In some cases, thesensor 104 can be embedded in the device 106. In some cases, the device106 may embed the sensor and an explicit sensor 104 can be omitted, andvice versa. In another example, the device 106 is an automobile. Thesensor 104 is configured to monitor vehicle data, such as engine data inthe automobile, and send the data to the CM 102. The engine data can beanalyzed to understand driving patterns and fuel consumption. Anotherexample of a sensor in an automobile is an accelerometer, which can beused to sense motion and report whether the automobile is moving orstationary.

The example communication system 100 includes the CM 102. The CM 102represents an application, set of applications, software, softwaremodules, hardware, or combination thereof that can be configured tocommunicate with the AN 110 for a machine type communication. The CM 102receives data from the sensor 104 or the device 106 and transmits thedata to the AN 110. In some cases, the CM 102 can be a MTC device. In ageneral description, the term “MTC device” can also refer to anyhardware and/or software component that can initiate and/or terminate acommunication session.

In some cases, the CM 102 can include a wireless modem or a wirelinemodem Examples of a wireline modem include a modem that is configured totransmit or receive data over a Digital subscriber line (DSL), anoptical cable, a coaxial cable, or any other wireline access technology.Examples of a wireless modem include a Wi-Fi modem, a Zigbee modem, asatellite modem, or a cellular modem. Examples of a cellular modeminclude a modem that can be configured to transmit and receive datausing Global System for Mobile communication (GSM), Interim Standard 95(IS-95), Universal Mobile Telecommunications System (UMTS), CDMA2000(Code Division Multiple Access), Evolved Universal MobileTelecommunications System (E-UMTS), Long Term Evaluation (LTE),LTE-Advanced, or any other radio access technology.

In some cases, a cellular modem may include circuit components, memorystorage units, and software for multiple radio access technologies,radio frequency components covering radio frequency bands, and otherperipheral interfaces. In some cases, the CM 102 can be implemented as alow-cost cellular modem that is configured for machine typecommunication. For example, the CM 102 may include a LTE modem withreduced functionality. In some cases, the LTE technology may offer abroad coverage across the globe. LTE technology may also provide higherdata rate at a lower cost. LTE technology is also suitable for thetransmission of bursty data and, therefore, provides an efficient wayfor multiple devices to share access to the AN 110. In some cases, theCM 102 may include an LTE MTC device (UE).

In some cases, the CM 102 may be configured to support a single radioaccess technology. For example, the CM 102 may be configured to supportLTE as the only radio access technology. The CM 102 may also beconfigured to support only a limited set of radio frequency bands and areduced protocol stack for a fixed device, e.g., without supporting theinter radio access transport handover. An example on inter radio accesstransport handover is the handover from a third generation (3G) to afourth generation (4G) radio transport. With the reduced radio frequencybands, elimination of the second generation (2G) and the thirdgeneration (3G) circuits, limited peripherals and I/O circuits,reduction of software and memory requirements, the cost of CM 102 can besignificantly reduced.

In some cases, the CM 102 can be configured to store, buffer, mark, ortag the data received from the sensor 104 or the device 106. In somecases, the CM 102 can also encrypt the data and communicate the datawith the AN 110. FIGS. 2-6 and associated descriptions provideadditional details of certain implementations.

The example communication system 100 also includes the AN 110. The AN110 represents an application, set of applications, software, softwaremodules, hardware, or combination thereof that can be configured tocommunicate with the CM 102 over an access interface and furthercommunicate with other elements of the example communication system 100over the Internet. The AN 110 can also be configured to communicate withthe CM 102 over a wireline access technology, e.g., Digital subscriberline (DSL), optical cable, a coaxial cable, or a wireline local areanetwork (LAN). The AN 110 can also be configured to communicate with theCM 102 over a wireless access technology, e.g., Wi-Fi, Zigbee,Bluetooth, personal area network (PAN), or any of the cellular accesstechnology discussed above. In one example, the AN 110 can be an LTEnetwork that includes one or more e-Node Bs (eNBs) and Evolved PacketCores (EPCs). In another example, the AN 110 can be a Wi-Fi accesspoint.

In some cases, the AN 110 can be a network that is operated by a mobilevirtual network operator (MVNO). Alternately or in combination, the AN110 can be operated by a traditional Cellular Operator. In some cases,the initial access procedure for a network that is operated by thetraditional Cellular Operator may be modified for establishing a machinetype communication.

As illustrated, the example communication system 100 also includes theDMS 120. The DMS 120 represents an application, set of applications,software, software modules, hardware, or combination thereof that can beconfigured to communicate with the CM 102 over the Internet cloud 130 tocontrol the machine type communication. For example, the DMS 120 can beconfigured to command the CM 102 to wake up, collect data, send the datato the DMS 120, and go to sleep.

The example communication system 100 also includes the applicationplatform 140. The application platform 140 represents an application,set of applications, software, software modules, hardware, orcombination thereof that can be configured to process the datatransmitted by the CM 102. In some cases, the application platform 140can be implemented on a server that is communicatively coupled with theDMS 120. Alternatively or in combination, the application platform 140can be implemented on the same platform as the DMS 120. In some cases,the application platform 140 can be configured to receive, sort,classify, and analyze data. In some cases, the application platform 140can be configured to create bills and reports. In some cases, theapplication platform 140 can support one or more vertical businesses,e.g., Health care, Retail, Automotive, Asset Tracking, Fleet Management,Metering, etc. Each of the vertical business can be supported by anapplication running on the application platform 140.

The example communication system 100 includes the AAS 122. The AAS 122represents an application, set of applications, software, softwaremodules, hardware, or combination thereof that can be configured toauthenticate the CM 102 and to provide an access manifest parameter forthe establishment of a machine type communication channel. In somecases, the AAS 122 can authenticate the CM 102 using a device identityof the CM 102. FIGS. 2-6 and associated descriptions provide additionaldetails of certain implementations.

In operation, the AN 110 receives a connection request for a machinetype communication from the CM 102. The connection request includes anauthentication credential for the CM 102. The AN 110 obtains a sharedsubscriber identity module (SIM) parameter for the machine typecommunication based on the authentication credential. In some cases, theAN 110 transmits the shared SIM parameter to the CM 102. The AN 110receives a registration request from the CM 102. The registrationrequest may include the shared SIM parameter. The AN 110 registers theCM 102 using the shared SIM parameter. The AN 110 receives a data packetfor the machine type communication from the CM 102. The AN 110 transmitsthe data to the DMS 120 and the DMS 120 forwards the data to theapplication platform 140. In some cases, the AN 110 may transmit thedata to the application platform 140 directly. FIGS. 2-6 and associateddescriptions provide additional details of both Uplink (UL) and Downlink(DL) transmissions.

While elements of FIG. 1 are shown as including various component parts,portions, or modules that implement the various features andfunctionalities, nevertheless these elements may instead include anumber of sub-modules, third-party services, components, libraries, andsuch, as appropriate. Furthermore, the features and functionality ofvarious components can be combined into fewer components as appropriate.

FIG. 2 is a message flow diagram 200 illustrating an example process forestablishing a machine type communication. The message flow diagram 200includes the CM 102, the AN 110, the DMS 120, and the AAS 122. In theillustrated example, the CM 102 is communicatively coupled with a sensorthat collects monitoring data. For example, the CM 102 can becommunicatively coupled with a smart meter that monitors the energyusage of a residence and collects data for the energy usage. In somecases, the smart meter can send the monitored data to the CM 102. Insome cases, the data can be sent over a serial link, a parallel link, ora USB link. For example, a low power link, e.g., a Transaction LayerPacket (TLP)/USB 2.0 Transceiver Macrocell Interface (UTMI) Low PinInterface (ULPI) link or an Inter-IC (I2C) link, can be used as thecommunication link between the smart meter and the CM 102. In somecases, the CM 102 can package the data for a machine type communication.For example, the CM 102 can include a time stamp that specifies a date,a time of collection, or both. The CM 102 can also include other relateddata, e.g., the location of the meter, the meter identity, the houseidentity, the temperature, or any combination thereof. In addition, theCM 102 can encrypt the machine type communication data package forsecurity.

At 202, the CM 102 initiates an attach procedure with the AN 110. Insome cases, the CM 102 can begin the attach procedure by sending aconnection request to the AN 110. The connection request can include anauthentication credential for the CM 102. The authentication credentialcan include an identity of the CM 102. Examples of the identity includesan International Mobile Subscriber Identity (IMSI), a SystemArchitecture Evolution (SAE) Temporary Mobile Subscriber Identity(S-TMSI), any other electronic equipment identifiers, or a combinationthereof. In some cases, the S-TMSI can include a Mobility ManagementEntity (MME) Temporary Mobile Subscriber Identity (M-TMSI) and an MMECode (MMEC). In some cases, the connection request can also include anindication that the connection is for a machine type communication.

At 204, the AN 110 sends an access request to the DMS 120. The accessrequest can indicate that an access for a machine type communication isrequested. In some cases, the access request can include theauthentication credential, e.g., the identity of the CM 102, in theconnection request that is received by the AN 110.

At 206, the DMS 120 sends an authentication request to the AAS 122. Insome cases, the authentication request can include the authenticationcredential of the CM 102. At 208, the AAS 122 authenticates the CM 102using the authentication credential. In some cases, the AAS 122 can usean Elliptic Curve Cryptography (ECC) certificate-based authenticationprocedure to perform the authentication procedures. An example of suchan authentication procedure includes using TLS (transport layersecurity) protocol using ECC certificates/signatures. In some cases, theauthentication credential may include a key, a certificate, a secret, asignature, or a combination thereof that is used in the authenticationprocedure. In some cases, the CM 102 may send a key, a certificate, asecret, a signature, or a combination thereof in addition to theauthentication credential. During the authentication procedures, the AAS122 can validate the CM 102 as an authorized device for a machine typecommunication. The AAS 122 can also verify that the CM 102 has anup-to-date subscription for the machine type communication based on astored profile of the CM 102.

At 210, the AAS 122 sends an authentication response to the DMS 120. Theauthentication response indicates whether the authentication issuccessful. If the authentication is not successful, the DMS 120 cansend an access response to the AN 110, and the AN 110 can terminate theattach procedure of the CM 102.

If the authentication is successful, the AAS 122 can include one or moreaccess manifest parameters in the authentication response message. Theaccess manifest parameters include parameters to establish acommunication channel between the CM 102 and the DMS 120. In oneexample, the access manifest parameters can include one or moresubscriber identity module (SIM) parameters. The one or more SIMparameters can be used to establish a connection over a cellularnetwork. In another example, the access manifest parameters can includea key or other unique identifier. The key can be used to establish aconnection over, e.g., a WiFi or a Zigbee network. In some cases, theAAS 122 can have access to a pool of access manifest parameters andselect an unoccupied access manifest parameter from the pool. Forexample, the AAS 122 can have access to a pool of shared SIM parameters.The AAS 122 can select a shared SIM parameter among the pool of sharedSIM parameters that are currently not used by another communicationmodule (CM), and include the selected shared SIM parameter in theauthentication response.

In some cases, the AAS 122 can encrypt the access manifest parametersand include the encrypted access manifest parameters in theauthentication response. For example, the AAS 122 can use the public keyof the CM 102 to encrypt the access manifest parameters.

At 212, the DMS 120 sends an access response to the AN 110. As discussedpreviously, if the authentication is not successful, the access responsemay indicate a rejection of the access request. If the authentication issuccessful, the access response can include the access manifestparameters that the DMS 120 receives from the AAS 122.

In some implementations, instead of sending the access manifestparameters to the DMS 120 so that the DMS 120 can forward the accessmanifest parameters to the AN 110, the AAS 122 can send the accessmanifest parameters directly to the AN 110.

At 214, the AN 110 sends a connection response to the CM 102. Theconnection response includes the access manifest parameters for the CM102. In some cases, as discussed previously, the access manifestparameters can be encrypted. In these or other cases, the CM 102 candecrypt the access manifest parameters.

At 216, the CM 102 establishes a communication channel with the DMS 120using the access manifest parameters. In some cases, the AN 110 can bethe access network that provides the communication channel. In oneexample, the AN 110 is a cellular network, e.g., an LTE network. The CM102 can send a registration request to the AN 110. The registrationrequest can include the access manifest parameters, e.g., a shared SIMparameter, that the CM 102 receives at 214. The AN 110 can use theaccess manifest parameters to register the CM 102 with the accessnetwork. Upon a successful registration, the AN 110 can establish acommunication channel for the CM 102. The CM 102 can send the datapackage of the machine type communication over the communication channelto the AN 110 and further to the DMS 120.

Alternatively, the CM 102 can use an access network that is differentthan the AN 110 to establish a communication channel with the DMS 120.In one example, the AN 110 is a Wi-Fi network, and the CM 102 uses theAN 110 to receive the access manifest parameters, e.g., a shared SIMparameter. The CM 102 can use the shared SIM parameter to register withan LTE network and transmit the machine type communication data packageto the DMS 120 using an LTE network. In another example, the AN 110 is acellular network, and the CM 102 uses the AN 110 to receive a sharedtoken or a shared key. The CM 102 can use the shared token or the sharedkey to register with a Wi-Fi or a Zigbee network and transmit themachine type communication data package to the DMS 120 using the Wi-Fior the Zigbee network.

In some cases, after the CM 102 completes the transmission of themachine type communication data package, the CM 102 can send aderegistration indication to the AN 110, delete the access manifestparameters, and go to sleep. In response to the deregistrationindication, the AN 110 can send a release message to the AAS 122.Alternatively or in combination, the DMS 120 can send a release messageto the AAS 122 after the DMS 120 has received the machine typecommunication data package from the CM 102. The release message mayinclude the access manifest parameters, the identity of the CM 102, or acombination thereof. The release message indicates that the accessmanifest parameters, e.g., the shared SIM parameter, can be released andused for other communication modules (CMs). Therefore, the accessmanifest parameters can be reused when another communication module (CM)requests a connection for a machine type communication.

In some cases, the AAS 122 can manage the pool of shared access manifestparameters independent of the release message. For example, the AAS 122may set a timer for each shared access manifest parameter that isassigned to a communication module (CM). The timer may be set accordingto an estimated time that may be used for the transmission of a machinetype communication data packet. When the timer expires, the AAS 122 candetermine that the assigned shared manifest parameter can be reused foranother communication module (CM).

By sharing access manifest parameters among multiple communicationmodules at different times, the cost for providing communicationchannels for machine type communication can be reduced. For example,assuming that 3 GB of data per month can be shared among 1000 devices,each device can transmit 3 MB of data per month. This is equivalent totransmitting 100 KB of data per day from each device. Further assumingthat the cost of 3 GB/month channel is around $20 for wholesalepurchase, the cost of service per device can theoretically be$20/1000=$0.02/device/month. Therefore, this approach significantlyreduces the cost of transmitting machine type communication data acrossa wide area of coverage. Alternately it may allow an enterprise to morefully utilize the data they buy by sharing the data usage betweendevices, but generally not at the same time.

In some cases, the AN 110 can establish a communication channel for theCM 102 without sending the access manifest parameters to the CM 102.FIG. 3 is a message flow diagram 300 illustrating another exampleprocess for establishing a machine type communication. The message flowdiagram 300 includes the CM 102, the AN 110, the DMS 120, and the AAS122. As discussed previously, the CM 102 is communicatively coupled witha sensor. The CM 102 receives monitored data from the sensor andpackages the data for a machine type communication.

At 302, the CM 102 initiates an attach procedure with the AN 110. Asdiscussed previously, the CM 102 can begin the attach procedure bysending a connection request to the AN 110. The connection request caninclude an authentication credential for the CM 102. At 304, the AN 110sends an access request to the DMS 120. In some cases, the accessrequest can include the authentication credential. At 306, the DMS 120sends an authentication request to the AAS 122. In some cases, theauthentication request can include the authentication credential of theCM 102. At 308, the AAS 122 authenticates the CM 102 using theauthentication credential. At 310, the AAS 122 sends an authenticationresponse to the DMS 120. As discussed previously, the authenticationresponse can include one or more access manifest parameters that can beused to establish a communication channel between the CM 102 and the DMS120. At 312, the DMS 120 sends an access response to the AN 110. Theaccess response can include the access manifest parameters.

In some cases, at 314, the AN 110 uses the access manifest parameters toestablish the communication channel for the CM 102 without sending theaccess manifest parameters to the CM 102. The AN 110 can register the CM102 using the access manifest parameters it receives and establish acommunication channel for the CM 102 once the registration issuccessful. At 316, the AN 110 can send a connection response to the CM102. The connection request indicates to the CM 102 that thecommunication channel has been established. At 318, the CM 102 can sendthe data package of the machine type communication over thecommunication channel to the DMS 120.

Storing the access manifest parameters in the AN 110 may provide one ormore advantages. For example, this approach may prevent a roguecommunication module (CM) from continuing to use the access manifestparameters after sending the machine type communication data packet.

FIG. 4 is a diagram illustrating an example layered protocol structure400 for establishing a machine type communication. The structure 400includes the CM 102, the AN 110, the DMS 120, the AAS 122, and theInternet cloud 130. As illustrated, the CM 102 communicates with the AN110 using a low-layer access protocol. In some cases, the low-layeraccess protocol is based on the access technology used by the AN 110. Inone example, the AN 110 is a LTE network and the access protocol istherefore the LTE access protocol. In another example, the AN 110 is aWi-Fi network and the access protocol is therefore the Wi-Fi protocol.The AN 110 communicates with the DMS 120 over the Internet cloud 130using a high-layer protocol, e.g., an Internet protocol. In some cases,the CM 102 can communicate with the DMS 120 using a low-overheadprotocol, e.g., a constrained command Session Initiation Protocol(SIP)-like protocol or Constrained Application Protocol (CoAP). In thiscase the payload is encapsulated with the low overhead protocol, whichin turn is encapsulated within the LTE access protocol. The LTE accessprotocol terminates in AN 110 and AN 110 then sends the payloadencapsulated with the low overhead protocol to the DMS 120. DMS 120 willhave a proxy that can extract the payload from the low overhead protocoland send it in the appropriate format for processing by the DMS 120. Insome cases the CM 102 can encapsulate the payload information in ahigher-level protocol like a TCP/IP packet, which is encapsulated withinthe LTE protocol. As described above the LTE protocol will terminate atAN 110 and AN 110 will then send the payload encapsulated with thehigher-level protocol to the DMS 120. The DMS 120 will have a proxy thatcan extract the payload from the low overhead protocol and send it inthe appropriate format for processing by the DMS 120.

In some cases, the DMS 120 can communicate with the AAS 122 using apropriety protocol. An Authentication and Access Manifest Grant Protocol(AAMGP) can be configured to transmit authentication requests andresponses discussed previously. In some cases, as discussed previously,the AN 110 may communicate with the AAS 122 directly, e.g., to receivethe access manifest parameters. In these or other cases, the AAS 122 canpackage the access manifest parameters in the AAMGP, and then furtherencapsulate the package in an Internet protocol and transmit to the AN110 over the Internet cloud 130.

FIG. 5 is a flowchart illustrating an example method 500 forestablishing a machine type communication. The method 500 may begin atblock 502, where a connection request for a machine type communicationis received from a MTC device. The connection request includes anauthentication credential for the MTC device. In some implementations,the MTC device may be a Long Term Evolution (LTE) MTC device that isconfigured for the machine type communication. At block 504, theauthentication credential is sent to a device management server (DMS).At block 506, a shared SIM parameter is received in response to theauthentication credential.

At block 508, the shared SIM parameter is transmitted to the MTC device.In some implementations, the shared SIM parameter may be encrypted by apublic key of the MTC device. In some implementations, a machine typecommunication channel for the MTC device may be established using theshared SIM parameter independent of sending the shared SIM parameter tothe MTC device.

At block 510, a registration request is received from the MTC device.The registration request includes the shared SIM parameter. At block512, the MTC device is registered with a cellular network using theshared SIM parameter. At block 514, a data packet is received from theMTC device for the machine type communication. At block 516, aderegistration indication is received from the MTC device. At block 518,in response to the deregistration indication, a release message is sent.The release message releases the shared SIM parameter.

FIG. 6 is a flowchart illustrating another example method 600 forestablishing a machine type communication. The method 600 may begin atblock 602, where a connection request for a machine type communicationis transmitted to an access network. The connection request includes anauthentication credential for the MTC device. In some implementations,the connection request is transmitted at a Long Term Evolution (LTE) MTCdevice that is configured for the machine type communication. At block604, a shared subscriber identity module (SIM) parameter for the machinetype communication is received in response to the connection request. Insome cases, the shared SIM parameter is encrypted. In these or othercases, the encrypted shared SIM parameter is decrypted. At block 606, aregistration request for a communication channel is transmitted. Theregistration request includes the shared SIM parameter. At block 608, aregistration response is received in response to the registrationrequest. The registration response grants a communication channel. Atblock 610, a data packet for the machine type communication istransmitted over the communication channel. In some implementations, thedata packet for the machine type communication is transmitted over theaccess network. At block 612, a deregistration indication istransmitted. The deregistration indication releases the shared SIMparameter.

Foregoing references to shared SIM parameters, access manifestparameters, and authentication credentials may include one or more of: apublic key; a private key; a certificate; a secret; a signature; a SIMIntegrated Circuit Card Identifier (ICCID), which may include an IssuerIdentification Number (IIN), Individual Account identification and acheck digit; an International Mobile Subscriber Identity (IMSI); anAuthentication key (K_(i)) Location area identity information; a ShortMessage Service Center (SMSC) number; System Architecture Evolution(SAE) Temporary Mobile Subscriber Identity (S-TMSI), which may include aMobility Management Entity (MME) Temporary Mobile Subscriber Identity(M-TMSI) and an MME Code (MMEC); or other parameters as may be needed inparticular circumstances. In an example, shared SIM parameters includeonly an IMSI and an authentication key.

While operations are depicted in the drawings in a particular order,this should not be understood as requiring that such operations beperformed in the particular order shown or in sequential order, or thatall illustrated operations be performed, to achieve desirable results.In certain circumstances, multitasking and parallel processing may beemployed. Moreover, the separation of various system components in theimplementation described above should not be understood as requiringsuch separation in all implementations, and it should be understood thatthe described program components and systems can generally be integratedtogether in a signal software product or packaged into multiple softwareproducts.

Also, techniques, systems, subsystems, and methods described andillustrated in the various implementations as discrete or separate maybe combined or integrated with other systems, modules, techniques, ormethods. Other items shown or discussed as coupled or directly coupledor communicating with each other may be indirectly coupled orcommunicating through some interface, device, or intermediate component,whether electrically, mechanically, or otherwise. Other examples ofchanges, substitutions, and alterations are ascertainable by one skilledin the art and could be made.

While the above detailed description has shown, described, and pointedout the fundamental novel features of the disclosure as applied tovarious implementations, it will be understood that various omissions,substitutions, and changes in the form and details of the systemillustrated may be made by those skilled in the art. In addition, theorder of method steps are not implied by the order they appear in theclaims.

What is claimed is:
 1. A method, comprising: receiving, from a machinetype communication (MTC) device, a connection request for a machine typecommunication, wherein the connection request includes an authenticationcredential for the MTC device; and obtaining a shared InternationalMobile Subscriber Identity (IMSI) for the machine type communicationbased on the authentication credential, wherein the shared IMSI isshared among a plurality of MTC devices.
 2. The method of claim 1,further comprising: transmitting, to the MTC device, the shared IMSI. 3.The method of claim 2, further comprising: receiving, from the MTCdevice, a registration request, wherein the registration requestincludes the shared IMSI; registering the MTC device with a cellularnetwork using the shared IMSI; and receiving, from the MTC device, adata packet for the machine type communication.
 4. The method of claim3, further comprising: receiving, from the MTC device, a deregistrationindication; and sending, in response to the deregistration indication, arelease message that releases the shared IMSI.
 5. The method of claim 2,wherein the shared IMSI that is transmitted to the MTC device isencrypted by a public key of the MTC device.
 6. The method of claim 1,further comprising: establishing, independent of sending the shared IMSIto the MTC device, a machine type communication channel for the MTCdevice using the shared IMSI.
 7. The method of claim 1, wherein theobtaining the shared IMSI comprises: sending the authenticationcredential to a device management server; and receiving, in response tothe authentication credential, the shared IMSI.
 8. The method of claim1, wherein the MTC device is a Long Term Evolution (LTE) device that isconfigured for the machine type communication.
 9. The method of claim 1,wherein the shared IMSI is stored in a network access node and isrefrained from being transmitted to the MTC device.
 10. The method ofclaim 1, wherein the connection request is transmitted using a lowoverhead high-layer protocol that is encapsulated in a Long TermEvolution (LTE) access message.
 11. The method of claim 1, wherein theconnection request is received over a first wireless network and theshared IMSI is used to establish communication for a second wirelessnetwork that uses a different radio access technology than the firstwireless network.
 12. The method of claim 11, wherein the first wirelessnetwork uses wireless local area network (WLAN) radio access technologyand the second wireless network uses Long Term Evolution (LTE) radioaccess technology. 13-20. (canceled)
 21. A device, comprising: a memory;and at least one hardware processor communicatively coupled with thememory and configured to: receive, from a Machine Type Communication(MTC) device, a connection request for a machine type communication,wherein the connection request includes an authentication credential forthe MTC device; and obtain a shared International Mobile SubscriberIdentity (IMSI) for the machine type communication based on theauthentication credential, wherein the shared IMSI is shared among aplurality of MTC devices.
 22. The device of claim 21, wherein the atleast one hardware processor is further configured to: transmit, to theMTC device, the shared IMSI.
 23. The device of claim 22, wherein the atleast one hardware processor is further configured to: receive, from theMTC device, a registration request, wherein the registration requestincludes the shared IMSI; register the MTC device with a cellularnetwork using the shared IMSI; and receive, from the MTC device, a datapacket for the machine type communication.
 24. The device of claim 23,wherein the at least one hardware processor is further configured to:receive, from the MTC device, a deregistration indication; and send, inresponse to the deregistration indication, a release message thatreleases the shared IMSI.
 25. The device of claim 22, wherein the sharedIMSI that is transmitted to the MTC device is encrypted by a public keyof the MTC device.
 26. The device of claim 21, wherein the at least onehardware processor is further configured to: establish, independent ofsending the shared IMSI to the MTC device, a machine type communicationchannel for the MTC device using the shared IMSI.
 27. The device ofclaim 21, wherein the obtaining the shared IMSI comprises: sending theauthentication credential to a device management server; and receiving,in response to the authentication credential, the shared IMSI.
 28. Thedevice of claim 21, wherein the MTC device is a Long Term Evolution(LTE) device that is configured for the machine type communication.29-40. (canceled)
 41. A tangible, non-transitory computer-readablemedium containing instructions which, when executed, cause a computingdevice to perform operations comprising: receiving, from a Machine TypeCommunication (MTC) device, a connection request for a machine typecommunication, wherein the connection request includes an authenticationcredential for the MTC device; and obtaining a shared InternationalMobile Subscriber Identity (IMSI) for the machine type communicationbased on the authentication credential, wherein the shared IMSI isshared among a plurality of MTC devices.
 42. (canceled)